Skip to content

Rescue: never drop the saved key, never fall back to pairing - #107

Merged
freethinkel merged 1 commit into
mainfrom
rescue-keep-key
Nov 20, 2026
Merged

freethinkel merged 1 commit into
mainfrom
rescue-keep-key

Conversation

@freethinkel

Copy link
Copy Markdown
Collaborator

A wedged watch that goes silent during auth (timeout waiting for 0x49) looked like a stale key, so connect() deleted the key and paired. Pairing waits for a tap the watch's dark screen can't take. A user in the field lost the only key that could reach their stuck watch this way.

  • On connect({ rescue: true }) the saved key is never deleted. An auth failure throws, and the rescue loop tries again on the next connection.
  • With no key, rescue never pairs. It stops at once with "no saved key for this watch in this browser — rescue can't pair…" (translated in messages.ts) instead of retrying.

Unit tests and the rescue and flash browser tests pass. check and lint are clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B

A wedged watch that goes silent during auth looked like a stale key, so
connect() deleted the key and paired, which waits for a tap the watch's dark
screen can't take. A user lost the only key that could reach their stuck
watch that way. On rescue the key is now kept on any auth failure (the loop
tries again), and with no key the page stops at once and says why.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B
@freethinkel
freethinkel merged commit 1fabb34 into main Nov 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant